System for changing setup of first device that executes predetermined function by second device and these devices

ABSTRACT

The user of an objective device registers a favorite setup of the objective device in a user setup data recording device in correspondence with user information based on a physical feature.  
     Upon detecting the physical feature of the user, the objective device sends its device ID to the user setup data recording device together with the user information based on the physical feature.  
     The user setup data recording device sends setup data of the objective device, which is set in advance by the user, to the objective device on the basis of the received user information and device ID. The objective device changes its setup on the basis of the received setup data.

FIELD OF THE INVENTION

[0001] The present invention relates to a system for changing the setupsof a first device, which executes a predetermined function, by a seconddevice, and these devices.

BACKGROUND OF THE INVENTION

[0002] Conventionally, many devices allow information setupscorresponding to user's requests and favor. For example, in a digitalcamera, many functions such as an aperture, shutter speed, whitebalance, exposure time, the way flash light is emitted, self-timer timeduration, presence/absence of date insertion, and the like can be set incorrespondence with user's favor.

[0003] Also, a system that can record several patterns of setup data ina device is available. When the user selects one of several patterns ofsetup data via some user interface, information is set in the device onthe basis of the selected setup data.

[0004] However, in the prior art, when many users use a single digitalcamera, and want to set it according to their favors, each user mustmanually re-input setup data. Furthermore, once a given user sets thedigital camera according to his or her favor, if another user sets upthe digital camera again, that user must also manually set up the cameraagain.

[0005] That is, currently available devices can be set according touser's favor. However, when another user sets up a given device again, agiven user must set up that device again according to his or her favor.Such case frequently occurs when a plurality of users use a commondevice.

[0006] The aforementioned system that can record several patterns ofsetup data forces the user to select one pattern. Furthermore, since thesystem can only record several patterns of setup data, it cannot copewith a case wherein many unspecific users want to use that device withoptimal setups.

SUMMARY OF THE INVENTION

[0007] It is an object of the present invention to allow easy setups ofa device.

[0008] It is another object of the present invention to obviate the needfor user's manual re-setup process every time the user re-uses thedevice which has been set once.

[0009] It is still another object of the present invention to identify auser who operates a device, and execute different processes forrespective users.

[0010] Other features and advantages of the present invention will beapparent from the following description taken in conjunction with theaccompanying drawings, in which like reference characters designate thesame or similar parts throughout the figures thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011]FIG. 1 is a block diagram showing the arrangement of aninformation setting unit built in a digital camera as an objectivedevice;

[0012]FIG. 2 is a block diagram showing the arrangement of a user setupdata recording device;

[0013]FIGS. 3A and 3B show a state wherein the user sets up variousfunctions of a digital camera;

[0014]FIG. 4 is a diagram showing setups of functions done between usersetup data recording devices and objective devices;

[0015]FIG. 5 is a timeline diagram between devices upon registration;

[0016]FIG. 6 is a flow chart showing the registration/setup processingsequence in the objective device;

[0017]FIG. 7 is a table showing data to be sent from the objectivedevice to the user setup data recording device upon registration;

[0018]FIG. 8 is a flow chart showing the registration/setup processingsequence in the user setup data recording device;

[0019]FIGS. 9A and 9B are timeline diagrams between devices upon settinguser setup data again;

[0020]FIG. 10 is a table showing data to be sent from the objectivedevice to the user setup data recording device when broadcast is notmade;

[0021]FIG. 11 is a table showing user setup data to be sent from theuser setup data recording device to the objective device as a reply uponsetting;

[0022]FIG. 12 is a flow chart showing the registration/setup processingsequence in the second embodiment;

[0023]FIG. 13 is a flow chart showing the registration/setup processingsequence in the third embodiment;

[0024]FIG. 14 is a block diagram showing characteristic functions of aninformation processing system according to the fourth embodiment of thepresent invention;

[0025]FIG. 15 is a block diagram showing another arrangement of anobjective device 1;

[0026]FIG. 16 is a block diagram showing still another arrangement ofthe objective device 1;

[0027]FIG. 17 is a block diagram showing the overall arrangement of asystem upon externally executing a level classification processaccording to each embodiment;

[0028]FIG. 18 is a block diagram showing the overall arrangement of asystem upon externally executing a level classification processaccording to each embodiment;

[0029]FIG. 19 is a flow chart showing the operation of the objectivedevice 1 of the fourth to ninth embodiments;

[0030]FIG. 20 is a flow chart showing the operation of the objectivedevice 1 of the fourth embodiment;

[0031]FIG. 21 shows the format of a database present in the objectivedevice 1 or an authentication server 3;

[0032]FIG. 22 is a block diagram showing characteristic functions of aninformation processing system according to the fourth to seventhembodiments of the present invention;

[0033]FIG. 23 shows the format of a database present in a user setupdata recording device 2;

[0034]FIG. 24 is a flow chart showing the operation of an objectivedevice 1 according to the fifth to seventh embodiments;

[0035]FIG. 25 shows the format of a database present in anauthentication server 3 according to the sixth embodiment;

[0036]FIG. 26 is a block diagram showing characteristic functions of aninformation processing system according to the eighth embodiment of thepresent invention;

[0037]FIG. 27 is a flow chart showing the operation of an objectivedevice 1 of the eighth embodiment;

[0038]FIG. 28 is a block diagram showing characteristic functions of aninformation processing system according to the ninth embodiment of thepresent invention;

[0039]FIGS. 29A and 29B show the format of a database present in a usersetup data recording device 2 according to the ninth embodiment;

[0040]FIG. 30 shows an image of how processing is executed according tothe ninth embodiment;

[0041]FIG. 31 is a flow chart showing the operation of an objectivedevice 1 of the ninth embodiment;

[0042]FIG. 32 shows the format of data to be sent to the user setup datarecording device 2 according to the ninth embodiment;

[0043]FIG. 33 shows another format of data to be sent to the user setupdata recording device 2 according to the ninth embodiment;

[0044]FIG. 34 shows an example of data to be sent from the user setupdata recording device to the objective device when the objective deviceis a network connection device;

[0045]FIG. 35 shows an example of data to be sent from the user setupdata recording device to the objective device when the objective deviceis a printer;

[0046]FIG. 36 shows an example of data to be sent from the user setupdata recording device to the objective device when the objective deviceis a device which is connected to a network via an access point;

[0047]FIG. 37 shows an example of data to be sent from the user setupdata recording device to the objective device when the objective deviceis a vehicle seat; and

[0048]FIG. 38 shows an example of data to be sent from the user setupdata recording device to the objective device when the objective deviceis a massage chair.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0049] Preferred embodiments of the present invention will be describedhereinafter with reference to the accompanying drawings. In thisembodiment, a device in which information is to be set is called an“objective device”, and a device which saves setup data of variousobjective devices and sets the data in the objective devices is called a“user setup data recording device”.

[0050] The user setup data recording device of this embodiment is ofwristwatch type, and the user wears it on a wrist. On the other hand,the objective device is a digital camera, which can be adjustedaccording to setup data by operating motors and the like on the basis ofthe setup data received from the user setup data recording device.Furthermore, a fingerprint sensor that measures a personal feature isused as a sensor.

[0051] First Embodiment

[0052]FIG. 1 is a block diagram showing the arrangement of aninformation setting unit built in a digital camera as an objectivedevice. An objective device 1 has an information setting unit in which aCPU 101, ROM 102, pattern matching unit 103, data converter 104, startupROM 105, flash ROM 106, fingerprint sensor 107, data receiver 112, anddata transmitter 113 are connected to a bus. The fingerprint sensor 107detects a fingerprint when a finger 4 is pressed against it. The datareceiver 112 and data transmitter 113 are connected to a wirelessinterface (I/F) 111, and exchange data with a user setup data recordingdevice 2 via a wireless channel 5. The objective device 1 has a powersupply unit 191, which is connected to a power supply 192, and supplieselectric power to respective units.

[0053]FIG. 2 is a block diagram showing the arrangement of the usersetup data recording device. The user setup data recording device 2 hasan arrangement in which a CPU 201, RAM 202, flash ROM 203, startup ROM204, data receiver 212, and data transmitter 213 are connected via abus. The data receiver 212 and data transmitter 213 are connected to awireless interface (I/F) 211, and exchange data with the objectivedevice 1 via the wireless channel 5. The user setup data recordingdevice 2 has a power supply unit 291, which is connected to a powersupply 292, and supplies electric power to respective units.

[0054]FIGS. 3A and 3B show a state wherein the user sets up variousfunctions of the digital camera. As illustrated in FIG. 3A, when afingerprint is detected by the fingerprint sensor 107 provided to ashutter button 8 upon pressing the shutter button 8 of the digitalcamera as the objective device 1, the objective device 1 receives setupdata from the user setup data recording device 2. As shown in FIG. 3B,zoom adjustment is done according to the received setup data.

[0055]FIG. 4 shows setups of functions done between user setup datarecording devices and objective devices. For example, when the usersetup data recording device 2 is user setup data recording device A (2a), the objective device 1 becomes objective device A (1 a) in whichsetup data from user setup data recording device A (2 a) are registered,by executing the operation shown in FIG. 3A. Likewise, when the usersetup data recording device 2 is user setup data recording device B (2b) or C (2 c), the objective device 1 becomes objective device B (1 b)or C (1 c) in which setup data from user setup data recording device B(2 b) or C (2 c) are registered, by executing the operation shown inFIG. 3A.

[0056] Registration Process

[0057] A process for registering data from the objective device 1 in theuser setup data recording device 2 will be explained first. FIG. 5 is atimeline diagram between the devices upon registration. The registrationsequence includes the following steps A, B, and C.

[0058] A. Authentication data is recorded in the user setup datarecording device.

[0059] The user registers authentication data in the user setup datarecording device 2 using a device exclusively used to recordauthentication data or the objective device 1. That is, a fingerprint ofthe user is read by the fingerprint sensor as physical information, andthe read data is converted into authentication data, which is sent toand recorded in the user setup data recording device 2 via the wirelesschannel. Note that the read data may be directly used as authenticationdata.

[0060] B. The user manually sets up the objective device.

[0061] The user turns on the power supply 192 of the objective device 1to start it up. Then, the user manually sets up the objective device 1.In this embodiment, since the objective device 1 is the digital camera,the user manually sets up functions of the digital camera such as ashutter speed, ON/OFF of AF (auto-focus), film speed (ISO 100/400), andthe like. Since the startup ROM 105 or flash ROM 106 stores a basic setof data to be set, the data set by the user (device setup data) arerecorded in the RAM 102.

[0062] C. The set device setup data is registered in the user setup datarecording device as user setup data.

[0063]FIG. 6 is a flow chart showing the registration/setup processingsequence in the objective device. This processing program is stored inthe startup ROM 105 in the objective device 1, and is executed by theCPU 101.

[0064] After the objective device 1 is set in an initial state byturning on the power supply 192, the user sets up the objective device,and waits until the fingerprint sensor 107 operates (step S1). The usermakes a registration start action, and presses the finger 4 against thefingerprint sensor 107 of the objective device 1. When the fingerprintsensor 107 is activated upon detecting touch with the finger 4, itchecks if the registration start action has been made (step S2).

[0065] As the registration start action, for example, the user pressesthe finger 4 against the fingerprint sensor 107 while pressing aregistration button equipped on the objective device 1, or the user tapsthe fingerprint sensor 107 twice, and presses the finger 4 against thefingerprint sensor 107 within 5 sec after the second tapping. Note thatthe registration start action is not particularly limited as long as itallows the user to explicitly instruct registration.

[0066] In this case, assume that the registration start action has beenmade, and the objective device 1 records information indicating thatdata which can be registered is to be sent (step S3). On the other hand,if the registration start action has not been made, the flow jumps tostep S4.

[0067] The objective device 1 checks if the fingerprint sensor 107 canacquire user's physical information (fingerprint) (step S4). If thephysical information can be acquired, the read physical information istemporarily recorded in the RAM 102, is converted into authenticationdata by the data converter 104, and the converted data is recorded inthe RAM 102 (step S5). Note that the physical information may bedirectly used as authentication data without being converted, and thedata conversion process may be skipped. In this case, the physicalinformation must be recorded by the same method as that whenauthentication data is recorded in the user setup data recording device2. When the CPU 101 can perform data conversion, the data converter 104may be omitted. Furthermore, the data conversion process may include asecurity process such as encryption or the like. The convertedauthentication data is stored in the RAM 102.

[0068] Note that by the process in step S3 the RAM 102 recordsinformation indicating whether or not the user wants to register. Morespecifically, information indicating whether or not the user has maderegistration is recorded. Also, the RAM 102 records user'sauthentication data by the process in step S5.

[0069] The objective device 1 checks with reference to data, which isstored in the RAM 102 and indicates whether or not registration has beenmade, if the authentication data is sent as data that can be registered(step S6).

[0070] In this case, since the user has made the registration action,and data that can be registered is to be sent, the authentication datastored in the RAM 102, device ID data registered by the manufacturer ofthe objective device in the startup ROM 105 or flash ROM 106, and devicesetup data manually set in the RAM 102 by the user are sent to the usersetup data recording device 2 (step S7). FIG. 7 shows data to be sentfrom the objective device to the user setup data recording device uponregistration.

[0071]FIG. 8 is a flow chart showing the registration/setup processingsequence in the user setup data recording device. This processingprogram is stored in the startup ROM 204 in the user setup datarecording device 2, and is executed by the CPU 201.

[0072] The user setup data recording device 2 is in an initial state.Upon receiving data sent from the objective device 1 (step S31), it ischecked if the received data contains device setup data (step S32). Ifthe device setup data is contained, that data is recorded in the usersetup data recording device 2 as user setup data. The user setup datarecording device 2 searches the contents of the flash ROM 203 using thereceived device ID data as a key, and if user setup data has alreadybeen recorded in correspondence with the received device ID, the device2 overwrites the received device setup data on that user setup data(step S33). If user setup data corresponding to the received device IDis not found, the device setup data is recorded in the flash ROM 203 incorrespondence with the received device ID (step S33) . After that, theflow returns to step S31.

[0073] Re-setup Process

[0074] The overall process upon setting again the user setup data storedin the user setup data recording device 2 in the objective device 1 willbe explained below. FIGS. 9A and 9B are timeline diagrams between thedevices upon setting user setup data again. FIG. 9A shows a case whereinthe objective device has already stored corresponding user setup data,and FIG. 9B shows a case wherein the objective device does not store anycorresponding user setup data.

[0075] The objective device 1 reads physical information data. The readdata is converted into authentication data. If the objective device 1can broadcast data, it sends only device ID data. Note that “broadcast”means communications with all of a plurality of user setup datarecording devices 2 that can communicate with the objective device 1 ifsuch devices 2 are present around the device 1. If the objective device1 does not broadcast data, it sends the authentication data and deviceID data. The objective device 1 records information indicating if itbroadcasted data.

[0076] The user setup data recording device 2 searches data in the usersetup data recording device 2 using the received device ID data as akey. If user setup data corresponding to the objective device 1 isfound, the device 2 sends that user setup data and device ID data. Onthe other hand, if user setup data corresponding to the objective device1 is not found, the device 2 sends no data.

[0077] If the objective device 1 broadcasts data, it receives aplurality of replies. The CPU 101 of the objective device 1statistically processes a plurality of received user setup data, andsets the statistically processed setup data again. On the other hand, ifthe objective device 1 does not broadcast data, since it receives onlyone data, the device 1 makes a re-setup process based on the single usersetup data. Such re-setup process is done in the following steps D, E,and F.

[0078] D. The objective device 1 sends device ID data alone or device IDdata and authentication data to the user setup data recording device 2.

[0079] As shown in FIG. 6 above, the user sets the objective device 1 inan initial state by turning on its power supply 192. The user pressesthe finger 4 against the fingerprint sensor 107 of the objective device1. When the fingerprint sensor 107 is activated upon detecting touchwith the finger 4 (step S1), it checks if a registration start actionhas been done (step S2). In this case, assume that the registrationstart action has not been done. Since the fingerprint sensor 107 iscombined with the shutter button 8, as shown in FIG. 3A, the usertouches the fingerprint sensor 107 which starts the re-setup processwithout his or her knowledge. Note that the user turns off thefingerprint sensor 107 in advance when he or she does not want to setdata again.

[0080] As described above, since the registration start action is notmade in this case, it is directly checked if physical information can beread (step S4). If read has failed, the control returns to the initialstate. On the other hand, if read has succeeded, the read data istemporarily saved in the RAM 102, and is converted into authenticationdata by the data converter 104 (step S5). If fingerprint information isdirectly used in personal identification without being converted intoauthentication data, this data conversion process may be skipped. Whenthe CPU 101 can perform data conversion, the data converter 104 may beomitted. Furthermore, the data conversion process may include a securityprocess such as encryption. The converted authentication data is storedin the RAM 102.

[0081] Since the registration start action has not been made, it isdetermined in step S6 that the data which can be registered is not to besent, and the objective device 1 then checks if it broadcasts device IDdata (step S8). Broadcast is made when the objective device 1 collectsfavors of a plurality of users, and sets data again by statisticallyprocessing the collected favors. Whether or not broadcast is made isdetermined by the manufacturer of the objective device 1. For example,as the objective device 1 that may be used in a situation whereinbroadcast is made, an air conditioner may be used. Note that the usermay select whether or not broadcast is to be made.

[0082] If broadcast is made, only the device ID data is sent (step S9).Data to be sent is obtained by excluding authentication data from datashown in FIG. 10 (to be described later). The objective device 1 recordsinformation indicating if broadcast has been made in the RAM 102.Whether or not broadcast is made is expressed by whether authenticationdata is appended or not to data to be transmitted.

[0083] On the other hand, if broadcast is not made, the objective device1 sends the authentication data stored in the RAM 102, and device IDdata stored in the startup ROM 105 or flash ROM 106 to the user setupdata recording device 2 (step S10). FIG. 10 shows data to be sent fromthe objective device to the user setup data recording device whenbroadcast is not made.

[0084] Since this embodiment uses a wireless communication means, ifdata is merely sent using an identical frequency, data is distributed toall objective devices 1 and user setup data recording devices 2 whichare present around the source objective device 1.

[0085] Therefore, in this embodiment, when authentication data isappended to data to be sent by the objective device 1, the user setupdata recording device 2 compares the received authentication data andthat held in advance, and if the two data match, the device 2 starts thesearch process; if they do not match, the device 2 discards the receiveddata. If authentication data is not contained in data sent by theobjective device 1, it is determined that the data is broadcast data,and the device 2 unconditionally starts the search process. In thiscase, the authentication data also serves as a transmission address.

[0086] In this embodiment, since the objective device 1 is the digitalcamera, broadcast is not made. Upon sending data, the authenticationdata stored in the RAM 102 is converted into an appropriatecommunication protocol in the CPU 101, and is sent via the datatransmitter 113 and wireless I/F 111 using the wireless channel 5.

[0087] E. The user setup data recording device 2 searches for user setupdata corresponding to the objective device 1, and if user setup datacorresponding to the objective device 1 is found, the device 2 sendsthat data; if corresponding data is not found, the device 2 sends nodata.

[0088] As shown in FIG. 8 above, the user setup data recording device 2is in an initial state. Upon receiving the sent data (step S31), it ischecked if the received data contains device setup data (step S32). Ifdevice setup data is not contained, the user setup data recording device2 sends corresponding data to the objective device 1.

[0089] It is then checked if the received data contains authenticationdata (step S34). If the authentication data is contained, the receivedauthentication data is collated with that which has already beenregistered in the flash ROM 203 (step S35). This collation is calledpersonal identification. It is checked as a result of personalidentification if two data match (step S36). If two data do not match,the control returns to the initial state, and no data is sent.

[0090] On the other hand, if it is determined as a result of personalidentification that two data match, i.e., if it is determined that theuser setup data recording device 2 belongs to the user who is currentlyusing that device, the contents of the flash ROM 203 are searched foruser setup data corresponding to the objective device 1 using thereceived device ID data as a key (step S37).

[0091] Since the device ID data contains the manufacturer name, productname, product category name, serial number, and the like, the search ismade using them as keywords. Normally, the best way of making the searchis to use the product name as a keyword. This is because even productsof an identical model, which have different serial numbers, may use usersetup data. However, the serial number or product category may be usedin comparison. The manufacturer of the user setup data recording device2 may determine device ID data to be used in the search or the user mayselect it.

[0092] As a result of search in step S37, if corresponding user setupdata is not found, the control returns to the initial state, and no datais sent. On the other hand, if corresponding user setup data is found,the found user setup data and device ID data are sent (step S38). Afterthat, the control returns to the initial state. FIG. 11 shows data to besent from the user setup data recording device to the objective deviceas a reply upon setting.

[0093] The received authentication data matches only for a user whosephysical information has been acquired by the fingerprint sensor. As aresult, even if a plurality of user setup data recording devices 2 arepresent around the objective device 1, data can be consequently sent tothe user setup data recording device 2 of a desired user.

[0094] F. When the objective device 1 can receive user setup data withina given period, it executes a re-setup process on the basis of that usersetup data.

[0095] As shown in FIG. 6 above, the objective device 1 waits forreception of user setup data within a predetermined period of time (stepS11). If user setup data cannot be received, the control returns to theinitial state; otherwise, it is checked if the received data is a replyto broadcast (step S12).

[0096] The objective device 1 recorded in the RAM 102 informationindicating if it broadcasted. Hence, if the objective device 1broadcasted, the received data is processed as a reply to broadcast;otherwise, the received data is processed as a reply from a single user.

[0097] In step S12, the objective device 1 compares to check if deviceID data contained in the received data matches its own device ID data.If the two data match, since the received data is a reply to the datasent by the objective device 1 itself, the subsequent process isexecuted; otherwise, the received data is discarded. Note that items ofthe device ID data to be actually compared are not specified in theabove description, but they may be determined by the manufacturer of theuser setup data recording device 2 or may be of user's choice.

[0098] If broadcast was made, a plurality of received user setup dataare statistically processed (step S13), and the objective device 1executes a re-setup process based on the statistical processing result(step S14). After that, the control returns to the initial state. On theother hand, if broadcast was not made, the objective device 1 executes are-setup process based on the received user setup data (step S15), andthe control returns to the initial state. In this embodiment, sincebroadcast was not made, the digital camera executes a re-setup processaccording to user's favor with reference to the user setup data (FIG.11) sent from the user setup data recording device 2.

[0099] Second Embodiment

[0100] In the first embodiment, upon registration in the objectivedevice, the user makes a registration start action first, then presses afinger against the sensor to generate authentication data, and sends thedata. Conversely, the user may press a finger against the sensor togenerate authentication data, and that data may be sent after aregistration start action is made. In the second embodiment, the lattercase will be explained in detail below.

[0101] Since an information setting system of the second embodiment hasthe same arrangement as the first embodiment, and only the order of theregistration start action and generation of authentication data isdifferent from the first embodiment, only different processes will beexplained. FIG. 12 is a flow chart showing the registration/setupprocessing sequence in the second embodiment. Since processes in step S5and the subsequent steps are the same as those in the first embodiment,a description thereof will be omitted by assigning the same step numbersthereto.

[0102] The user presses the finger 4 against the fingerprint sensor 107of the objective device 1 in the initial state, and waits until thefingerprint sensor 107 is activated (step S1). After the fingerprintsensor 107 is activated, it is checked if physical information(fingerprint information) can be sampled (step S2A). If physicalinformation cannot be sampled, the flow returns to step S1.

[0103] On the other hand, if physical information (fingerprintinformation) can be sampled, that information is converted intoauthentication data, and the converted data is recorded in the RAM 102(step S3A).

[0104] After that, the control waits for a predetermined period of time(step S3B), and it is checked if a registration start action has beenmade during that period (step S4A). If a registration start action hasnot been made during the predetermined period of time, it is determinedthat a re-setup process is to be done, and processes in step S6 and thesubsequent steps are executed. On the other hand, if the registrationstart action has been made during the predetermined period of time,information indicating that data which can be registered is to be sentis recorded in the RAM 102 (step S5A), and the flow advances to step S6.

[0105] In the second embodiment, the control waits for a predeterminedperiod of time, if the registration start action has been made duringthat period, information indicating that data which can be registered isto be sent is recorded in the RAM 102, and the flow advances to step S6.On the other hand, if the registration start action has not been made,the flow jumps to step S6. After a predetermined period of time, it ischecked with reference to the RAM 102 if information indicating thatdata which can be registered is to be sent is recorded.

[0106] In this way, authentication data may be generated first, and itis then checked if the registration start action has started.

[0107] Third Embodiment

[0108] In the third embodiment, the user presses the finger against thesensor to generate authentication data first, and data is sent after aregistration start action is made, as in the second embodiment. FIG. 13is a flow chart showing the registration/setup processing sequence inthe third embodiment. Note that the same step numbers denote the samestep processes as those in the second embodiment.

[0109] That is, after sampled physical information (fingerprintinformation) is converted into authentication data, and the converteddata is recorded in the RAM 102 in step S3A, the control makes the userexplicitly select a registration start action or re-setup action (stepS4B). For example, a registration button and re-setup button areprovided to the objective device 1, and the control prompts the user topress one of them.

[0110] If the user has pressed the registration button, informationindicating that data which can be registered is to be sent is recordedin the RAM 102 (step S5A), and the flow advances to step S6. On theother hand, if the user has pressed the re-setup button, the flow jumpsto step S6. Irrespective of the button selected by the user, theobjective device 1 checks with reference to the RAM 102 in the processin step S6 if data which can be registered is to be sent.

[0111] In this manner, authentication data may be generated first, andit is then checked if the registration start action has started or ifthe re-setup action has been made.

[0112] Fourth Embodiment

[0113] This embodiment will explain a case wherein a levelclassification process for identifying a user who accesses the objectivedevice 1 and executing a different process for each user is executed, asshown in FIG. 14. A case will be explained below wherein anauthentication process for the user is made as the level classificationprocess.

[0114] Also, in this embodiment, objective devices with the arrangementsshown in FIGS. 15 and 16 will be explained in addition to the objectivedevice 1 shown in FIG. 1.

[0115] In the arrangement of an objective device 1 shown in FIG. 15, aLAN I/F 114 and modem 115 are added to the arrangement shown in FIG. 1,and the pattern matching unit 103 is excluded therefrom.

[0116] In the arrangement of an objective device 1 shown in FIG. 16, aLAN I/F 114 and modem 115 are added to the arrangement shown in FIG. 1.

[0117] The arrangement of the objective device 1 changes slightlydepending on whether to execute the level classification process insideor outside the objective device. When the level classification processis executed internally, any of the arrangements shown in FIGS. 1, 15,and 16 can be used; when the level classification process is executedexternally, either the arrangement shown in FIG. 15 or 16 is used. Ofcourse, when the level classification process is externally executed viaa wireless channel without using the LAN I/F 114 and modem 115, any ofthe arrangements shown in FIGS. 1, 15, and 16 may be used.

[0118] When the level classification process is executed internally, thearrangement of the overall system including the objective device 1 anduser setup data recording device 2 is the same as that shown in FIG. 4.However, when the level classification process is executed externally,the arrangement shown in FIG. 17 or 18 is adopted. In the overallarrangement shown in FIG. 4, objective devices 1 a, 1 b, 1 c, . . . anduser setup data recording devices 2 a, 2 b, 2 c, . . . are connected toeach other via wireless channels. In the overall arrangement shown inFIG. 17, objective devices 1 a, 1 b, 1 c, . . . are connected to theauthentication server 3 via a LAN (Local Area Network) 6 or publicnetwork 7. In the arrangement shown in FIG. 18, an objectivedevice/authentication server 1 aa is provided in place of theauthentication server 3 in the arrangement shown in FIG. 17.

[0119] The arrangement of the user setup data recording device 2 is asshown in FIG. 2.

[0120] In this embodiment as well, assume that the user wears awristwatch type user setup data recording device 2 on a wrist. The userneed not always wear the device 2 on a wrist, but must hold it at aposition where the device 2 can communicate with the objective device 1.A digital camera incorporates the objective device 1, and is adjustedaccording to setup data received from the user setup data recordingdevice 2 by operating motors and the like based on the received setupdata.

[0121] In this embodiment, the digital camera and wristwatch are assumedas forms of the objective device 1 and user setup data recording device2. However, the present invention can be used when they have otherforms. For example, examples of the objective device 1 include anillumination appliance, sound system, seat, and the like in addition tothe digital camera, and examples of the user setup data recording device2 include a portable telephone, PDA (Personal Digital Assistant),portable music player, and the like. Note that items of device setupdata exchanged between the objective device 1 and user setup datarecording device 2 differ depending on the types of objective devices 1.For example, when the objective device 1 is a sound device, items “tonevolume”, “surround mode type (film theater, hall, and the like)”,“loudspeaker direction”, and the like are used in place of items“shutter speed”, “AF ON/OFF”, and the like.

[0122] The operation of the objective device 1 according to thisembodiment will be described below with reference to the flow charts inFIGS. 19 and 20. Note that the operation of the user setup datarecording device 2 is the same as that explained above with reference toFIG. 8. Also, the registration operation is the same as that in thefirst embodiment.

[0123] <Re-setup Operation>

[0124] The re-setup operation of this embodiment will be describedbelow.

[0125] The flow of overall processes executed in the re-setup operationwill be briefly explained first.

[0126] The objective device 1 reads physical information data. The readdata is converted into authentication data. An authentication process isdone to authenticate if the user has the right of use of the objectivedevice 1. When broadcast is to be made, device ID data alone is sent;when broadcast is not to be made, authentication data and device ID dataare sent. The objective device 1 records information indicating that itbroadcasted data or sent data to a plurality of users.

[0127] The user setup data recording device 2 searches data thereinusing the received device ID data as a key. If user setup datacorresponding to the objective device 1 is found, the device 2 sendsthat data and device ID data; if such data is not found, the device 2sends no data.

[0128] If the objective device 1 broadcasted or sent data to a pluralityof users, it receives a plurality of replies. The objective device 1statistically processes a plurality of received user setup data, andexecutes a re-setup process based on the statistical processing result.If the objective device 1 neither broadcasted nor sent data to aplurality of users, since it receives only one data, the device 1executes a re-setup process on the basis of single user setup data.

[0129] The flow of the re-setup process will be described in detailbelow.

[0130] The timeline diagram between the devices in the re-setup processis the same as that shown in FIG. 9.

[0131] (1) Generation of authentication data by objective device 1

[0132] Referring to FIG. 19, the objective device 1 is set in an initialstate by turning on the power supply 192. The user presses the finger 4against the fingerprint sensor 107 of the objective device 1. Thefingerprint sensor 107 is activated by detecting that touch (step S1).After the sensor 107 is activated, it is checked if a registration startaction has been made (step S2). Assume that a registration start actionhas not been made in this case.

[0133] When the fingerprint sensor 107 is combined with a shutterbutton, the user can start a setup process by touching the fingerprintsensor 107 without his or her deliberate action. Of course, when theuser does not want to execute a re-setup process proposed by the presentinvention, he or she need only turn off the sensor.

[0134] Physical information is then read (step S4). If read has failed,the control returns to the initial state. On the other hand, if read hassucceeded, the read data is temporarily saved in the RAM 102, and isconverted into authentication data by the data converter 104 (step S5).If fingerprint information is directly used in personal identificationwithout being converted into authentication data, this data conversionprocess may be skipped. When the CPU 101 can perform data conversion,the data converter 104 may be omitted. Furthermore, the data conversionprocess may include a security process such as encryption. The convertedauthentication data is stored in the RAM 102.

[0135] (2) Authentication process of objective device 1

[0136] An authentication process is done inside or outside the objectivedevice 1. When the authentication process is done inside the objectivedevice 1, e.g., when fingerprint authentication is done using thepattern matching unit 103, the objective device 1 must have thearrangement shown in FIG. 1 or 16. If authentication is done by the CPU101 without using the pattern matching unit 103, any of the arrangementsshown in FIGS. 1, 15, and 16 may be used irrespective of thepresence/absence of the pattern matching unit 103.

[0137] When the authentication process is done outside the objectivedevice 1 using the LAN 6, public network 7, or wireless channel 5, adevice that executes fingerprint authentication such as theauthentication server 3 in FIG. 17 or the objectivedevice/authentication server 1 aa in FIG. 18 is required on the network,and the objective device 1 must have a function capable of accessingsuch device. When fingerprint authentication is externally executed, theobjective device 1 is added with components such as a LAN I/F 114, modem115, and the like if necessary. Of course, if the objective device 1 cancommunicate with the authentication server 3 using the wireless I/F 111,the need for the LAN I/F 114, modem 115, and the like can be obviated.That is, when the authentication process is executed outside theobjective device 1, the authentication server 3 need only communicatewith the objective device 1.

[0138] A supervisor of the objective device 1 must set in the objectivedevice 1 information indicating whether fingerprint authentication isdone inside or outside the objective device 1, in correspondence withthe structure and operating environment of the objective device 1. Instep S1901, this information is checked. Assume that the objectivedevice 1 itself or the external authentication server 3 (includinganother objective device 1 having an authentication server function)includes a database shown in, e.g., FIG. 21.

[0139] When fingerprint authentication is executed inside the objectivedevice 1, the pattern matching unit 103 compares authentication data,which is generated by acquiring fingerprint information by the sensorand is stored in the RAM 102, with authentication data, which arealready registered in the flash ROM 106, thereby checking if the userwho operates the objective device 1 has the right of use of theobjective device 1 (step S1904). If the flash ROM 106 storesauthentication data which matches that in the RAM 102, the user has theright of use of the objective device 1; otherwise, the user does nothave such right.

[0140] If fingerprint authentication is done outside the objectivedevice 1, the objective device 1 sends the authentication data to theauthentication server 3 or objective device/authentication server 1 aa(step S1902). The authentication server 3 or objectivedevice/authentication server 1 aa receives the authentication data,authenticates by comparing it with authentication data which areregistered in advance, and sends the authentication result to the sourceobjective device 1. The objective device 1 receives the fingerprintauthentication result (step S1903). It is checked based on the receivedresult if the user has the right of use (step S1904). If the user hasthe right of use, the flow advances to step S2001 in FIG. 20; otherwise,the control returns to the initial state.

[0141] (3) Transmission of device ID data alone or device ID data andauthentication data by objective device 1

[0142] The objective device 1 then checks if it broadcasts device IDdata (step S2001). Note that “broadcast” means communications with allof a plurality of user setup data recording devices 2 that cancommunicate with the objective device 1 if such devices 2 are presentaround the device 1.

[0143] Broadcast is made when the objective device 1 collects favors ofa plurality of users, and executes a re-setup process by statisticallyprocessing the collected favors. Whether or not broadcast is to be madeis determined by the manufacturer of the objective device 1. As theobjective device 1 that may be used in a situation wherein broadcast ismade, an air conditioner may be used. Note that the user may selectwhether or not broadcast is to be made.

[0144] If broadcast is not to be made, the objective device 1 sends theauthentication data stored in the ROM 102 and device ID data stored inthe startup ROM 105 or flash ROM 106 to the user setup data recordingdevice 2 (step S2003). Data to be sent is as shown in FIG. 10.

[0145] If broadcast is to be made, the objective device 1 sends deviceID data alone. Data to be sent in this case is obtained by excludingauthentication data from that shown in FIG. 10. Also, various otherbroadcast processes may be used. For example, if a predetermined fieldof data to be sent stores text “broadcast”, it can be determined thatthe data is broadcasted. Also, a flag which is set upon broadcasting maybe prepared as one item of transmission data, and if that flag is 1, itmay be determined that the data is broadcast data; otherwise, the datais not broadcast data.

[0146] The objective device 1 records in the RAM 102 informationindicating if broadcast was made. Whether or not broadcast is made isexpressed by whether authentication data is appended or not to data tobe transmitted. Since this embodiment uses a wireless communicationmeans, if data is merely sent using an identical frequency, data isdistributed to all objective devices 1 and user setup data recordingdevices 2 which are present around the source objective device 1.

[0147] Therefore, in this embodiment, when authentication data isappended to data to be sent by the objective device 1, the user setupdata recording device 2 compares the received authentication data andthat held in advance, and if the two data match, the device 2 starts thesearch process; if they do not match, the device 2 discards the receiveddata. Upon receiving broadcast data which does not contain anyauthentication data and in which the broadcast flag is set, the device 2unconditionally starts the search process.

[0148] In this way, the authentication data also serves as atransmission address.

[0149] In this embodiment, assume that broadcast is not made. Uponsending data, the authentication data stored in the RAM 102 is convertedinto an appropriate communication protocol in the CPU 101, and is sentvia the data transmitter 113 and wireless I/F 111 using the wirelesschannel 5.

[0150] After the data is sent (step S2003), it is checked if identicaldevice ID data is to be sent to a plurality of users (step S2004). Thechecking process in step S2004 is effective when the setups of onlygiven group members are to be reflected in a given objective device 1 inplace of setups of unspecified users within the communication range ofthe objective device 1. This process is equivalent to checking in theInternet environment if unicast is to be done a plurality of number oftimes.

[0151] If it is determined in step S2004 that the data is to be sent toa plurality of users, the authentication data is replaced by that forthe group members (step S2005), and the replaced data is sent (stepS2003). The authentication data for the group members is set in advancein the objective device 1. In this embodiment, assume that data is notsent to a plurality of users.

[0152] Upon receiving the device ID data and the like sent from theobjective device 1, the user setup data recording device 2 sends backuser setup data by executing the processes shown in FIG. 8.

[0153] The objective device 1 checks if it can receive the user setupdata sent from the user setup data recording device 2 within apredetermined period (step S2006). If the objective device 1 cannotreceive any data within the predetermined period, the control returns tothe initial state without any process.

[0154] If the objective device 1 receives the user setup data, it checksbased on information which is recorded in the ROM 102 and indicateswhether or not it broadcasted data or sent data to a plurality of usersif the received user setup data is a reply to the broadcast data or fromthe plurality of users, or a reply from a single user (step S2007).

[0155] The objective device 1 compares if device ID data contained inthe received data matches its own device ID data. If the two data match,since the received data is a reply to the data sent by the objectivedevice 1 itself, the subsequent process is executed; otherwise, thereceived data is discarded. Note that items of the device ID data to beactually compared in a search are not specified in the abovedescription, but they may be determined by the manufacturer of the usersetup data recording device 2 or may be of user's choice.

[0156] If it is determined in step S2007 that the received data is areply from a single user, the objective device 1 is set up again basedon the received user setup data (step S2010), and the control returns tothe initial state.

[0157] If the received data is a reply to the broadcast data or from theplurality of users, a statistical process of a plurality of receiveduser setup data is executed (step S2008), and the objective device 1 isset up again based on the statistical processing result (step S2009) .After that, the control returns to the initial state.

[0158] In this embodiment, since broadcast is not made, the digitalcamera is set up again according to user's favor with reference to theuser setup data in the data which is sent from the user setup datarecording device 2, as shown in FIG. 11.

[0159] Fifth Embodiment

[0160]FIG. 22 is a block diagram showing characteristic functions of aninformation processing system according to the fifth embodiment of thepresent invention.

[0161] This embodiment will explain a case wherein an objective device 1executes a process corresponding to the level of data received from auser setup data recording device 2, as shown in FIG. 22, as an exampleof a process for identifying a user who accesses the objective device 1,and executing a process for each user. That is, a service which isprovided when a database in FIG. 23 is prepared in the user setup datarecording device 2, and the objective device 1 changes its processaccording to data obtained by searching the database will be explained.

[0162] The flow charts showing the operation of the objective device 1according to this embodiment use those shown in FIGS. 19 and 24. Thedifference between FIG. 24 and FIG. 20 used in the fourth embodiment isthat a process in step S2400 is added between steps S2007 and S2010.

[0163] The aforementioned differences of this embodiment will besupplemented.

[0164] The database shown in FIG. 23 is characterized in that the usersetup data recording device 2 holds use histories for respective deviceID data in addition to authentication data and device ID data. The usehistory is updated when the fingerprint sensor 107 of the objectivedevice 1 responds to the user, data shown in FIG. 10 is sent from theobjective device 1 to the user setup data recording device 2, twoauthentication data match upon comparison, and user setup data is foundby searching data in the user setup data recording device 2 using deviceID data.

[0165] For example, assuming that the objective device 1 is a digitalcamera, and data shown in FIG. 10 is sent, a use history of a key whichmatches device ID data in FIG. 10 is incremented by 1 in the databaseshown in FIG. 23. More specifically, use history values corresponding to“CANON”, “Digital Camera”, “Auto Set”, and “ASC-0000001” are incrementedby 1, and are updated from 15 to 16, 20 to 21, 43 to 44, and 55 to 56,respectively. Of course, other processes such as a decrement process maybe used in place of the increment process, and the increment value isnot limited to 1. Assume that this process is defined in advance in theuser setup data recording device 2.

[0166] When the user setup data is sent from the user setup datarecording device 2 to the objective device 1, authentication data, usersetup data, and use history values corresponding to respective keys ofdevice ID data are sent together.

[0167] The objective device 1 receives data (step S2006), and checks ifthe received data is a reply to broadcast data or from a plurality ofusers (step S2007). In this embodiment, assume that the received data isnot a reply to broadcast data or from a plurality of users.

[0168] The objective device 1 collates the received authentication datawith that temporarily recorded in step S5 in FIG. 19 to check if thereceived data is a reply from the user who used the objective device 1immediately before the current process (step S2400). If the receiveddata is a reply from that user, a service to be provided to that user isselected with reference to the received use history (step S2400), and asetup process corresponding to the selected service is executed (stepS2010). For example, a discount service for registering charge data bydiscounting it 20% if the use history indicates 10 times or more can beprovided.

[0169] As described above, when the user setup data recording device 2holds the database shown in FIG. 23, the following advantages areexpected compared to a case wherein the database is prepared in theauthentication server 3. The use history can be recorded in the usersetup data recording device 2 independently of whether or not theobjective device 1 is connected to the network. That is, themanufacturer that provides the objective device 1 to the user canprovide services irrespective of the use environment of the objectivedevice 1.

[0170] The main feature of this embodiment lies in that the database isheld in the user setup data recording device 2. The database can recordnot only the use history but also the use date, location, and the likedepending on the setups of processes done by the user setup datarecording device 2.

[0171] With the mechanism proposed by this embodiment, the manufacturerof the objective device 1 or a provider which provides services usingthe objective device 1 can provide services irrespective of the settingenvironment of the objective device 1. Also, the use states of users canbe recognized more accurately, and can be reflected in the developmentof products more suitable for user's needs.

[0172] Also, since use records can be automatically stored in the usersetup data recording device 2 without any user's operation, the usernever forgets to count the number of times of use, and can have manyopportunities of receiving better services from the manufacturers andthe like.

[0173] Sixth Embodiment

[0174] This embodiment will explain a case wherein a processcorresponding to the level of data received from the user setup datarecording device 2 is executed, e.g., data corresponding to levels arestored in the authentication server 3, and different services areprovided for respective users, as shown in FIG. 22, as an example of aprocess for identifying a user who accesses the objective device 1, andexecuting a process for each user. The flow charts of the objectivedevice 1 of this embodiment use FIGS. 19 and 24.

[0175] In the fourth embodiment, FIG. 21 is used as an example of thedatabase in the authentication server 3, and when the user touches thesensor 107 of the digital camera (objective device 1), authenticationand personal identification are done to make setups according to theuser. This embodiment will explain services which can be provided when adatabase shown in FIG. 25 is prepared in the authentication server 3 inaddition to that shown in FIG. 21.

[0176] More specifically, services provided when the user touches thesensor 107 to make the objective device 1 look up the database of theauthentication server 3 that records user information, and executedifferent processes for respective users will be explained.

[0177] In the fourth embodiment, when authentication is made outside theobjective device 1, authentication data shown in FIG. 10 is sent to theauthentication server 3. Since the authentication data shown in FIG. 10matches registered data of Taro Yamada in the database shown in FIG. 21,it is determined that the user is Taro Yamada, the user ID is 12345, thegender is male, charge data is 2000 yen, and so forth, and Taro Yamadais authenticated as the user who has the right of use of the objectivedevice 1. In this embodiment, data to be sent from the objective device1 to the authentication server 3 contains authentication data and deviceID data. That is, the data shown in FIG. 10 is sent.

[0178] Assume that a database having data shown in FIG. 25 is present inthe authentication server 3. The database need not always be present inthe server as long as it can be accessed by the authentication server 3on the network. FIG. 25 shows the user ID for only one user, but theauthentication server 3 can store and manage a plurality of user IDs.

[0179] In this embodiment, the authentication server 3 authenticates bycomparing authentication data sent from the objective device 1 with thatwhich is held in advance in the server as in the fourth embodiment. Theauthentication process is to compare authentication data. In thisembodiment, when the database shown in FIG. 21 is looked up usingauthentication data as a key, the user ID and the like can be revealed.When the database is searched using the user ID “12345” as a keyword,user data shown in FIG. 25 is found. At this time, management for eachuser is not limited to the user ID, but other keywords such as the username and the like can be used as long as they can specify the user. Ofcourse, authentication data can be used.

[0180] In the database shown in FIG. 25, the user ID “12345” has foursets of information such as use permission device ID data, servicelevel, and use history. The user ID may have five or more sets ofinformation. The use permission device ID data is ID data of the devicethe user is granted permission of use. The service level is the level ofa service the user can receive when he or she uses the use permissiondevice ID data; S is the highest service level and E is the lowestservice level. The service level lowers in the order of S, A, B, C, D,and E. The use history indicates the number of times the user used theobjective device 1 having the use permission ID data.

[0181] Hence, the user ID “12345” can use the use permission device IDdata “ASC-0000001” at the service level “S”, and the use historyindicates “15” times.

[0182] The authentication server 3 searches for data corresponding tothe level, as described above, and sends the service level to theobjective device 1. The objective device 1 receives the service level,and temporarily saves it. After that, upon receiving user setup data viaa communication with the user setup data recording device 2, theobjective device 1 executes a process corresponding to the saved servicelevel (step S2400 in FIG. 24).

[0183] The process corresponding to the service level includes a processfor, e.g., limiting the use time of the digital camera (objective device1) to one week for the service level S (highest) or to 30 min for theservice level E (lowest). The objective device 1 executes such setup onthe basis of the service level (step S2010).

[0184] Personal information such as use permission device ID data, usehistory, or the like is helpful data for product development and salesof the manufacturer, which can acquire such data without the knowledgeof the user. The service level of the user changes depending on the usehistory and the like; when the user repetitively uses an identicalproduct or manufacturer, the service level rises, and the user canreceive better services.

[0185] For example, assume that the objective device 1 is a digitalcamera, and the objective device 1 managed by the authentication server3 is a rental digital camera. The manufacturer lends the user the rentaldigital camera, and can collect a use fee. In this case, when the usermakes registration in the authentication server 3 in advance, he or sheneed only touch the sensor of the digital camera to effect a hireprocess.

[0186] More specifically, when the user touches the sensor,authentication data is transferred to the authentication server 3 toexecute an authentication process. At this time, rental data such as arental time, model, and the like are saved in the authentication server,thus completing the rental process.

[0187] Also, the number of photos that can be taken by that digitalcamera is unlimited for the service level S, 40 for A, 20 for B, 10 forC, 5 for D, and 2 for E. In FIG. 25, the user with the user ID “12345”can unlimitedly take photos with a camera corresponding to usepermission ID data “ASC-0000001”, 40 photos with a camera “Auto Set”, 20photos with a camera “Digital Camera”, and so forth. In this way,flexible service levels can be set based on use permission device IDdata. The manufacturer can recognize the use histories of the respectiveusers and can provide better services to a user who uses products ofthat manufacturer, and the user can enjoy such services.

[0188] The aforementioned mechanism can be variously applied. Forexample, a service type may be used in place of the service level, and aservice that the user receives may be changed depending on that type.Alternatively, charge data may be multiplied by a given discount ratedepending on the use history to provide a bargain service. Also, thedatabase in FIG. 25 may be segmented to save user setup data ofindividual users, and statistical data indicating the ways the objectivedevice 1 is used can be acquired.

[0189] Users may be categorized into groups laid down by a serviceprovider, and services corresponding to groups may be provided. Forexample, different services may be provided depending on whether theuser belongs to a male or female group, or whether the user belongs to acourtesy or regular member group. In this way, different servicescorresponding to different groups can be provided.

[0190] As described above, according to this embodiment, when thedatabase shown in FIG. 25 is added to the authentication server 3, themanufacturer can provide various services, and the user can enjoy suchservices.

[0191] Seventh Embodiment

[0192] This embodiment will explain a case wherein different servicesare provided by storing data in the user setup data recording device 2,and changing the number of data acquired by the objective device 1 foreach user, as shown in FIG. 22, as an example of a process foridentifying a user who accesses the objective device 1, and executing aprocess for each user.

[0193] For example, assume that device setup data for a given objectivedevice 1 contains 10 items (shutter speed, AF ON/OFF, ISO 100/400, andthe like if the objective device 1 is, e.g., a digital camera). A methodof providing a service that limits the number of items which can be useddepending on users in such circumstance (for example, an objectivedevice 1A allows user α to make setups using all 10 items of theobjective device 1, but allows user β to make setups using only threeitems) will be explained.

[0194] The objective device 1 according to this embodiment changes itemsused in setups depending on users in step S2400 in FIG. 24. For thispurpose, the objective device 1 or the authentication server 3 that cancommunicate with the objective device 1 saves data for ranking users,and processes executed in correspondence with the ranks of users.

[0195] For example, the user rank includes S (highest), A, B, C, and D(lowest) . In the process corresponding to the user rank, if devicesetup data of a given objective device 1 has 10 items, the user of rankS can make setups of the objective device 1 using all the 10 items, theuser of rank A can use 8 items, the user of rank B can use 6 items, theuser of rank C can use 4 items, and the user of rank D can use only 2items. Upon executing this process, the objective device 1 may receiveand process user setup data of all the 10 items from the user setup datarecording device 2, or may receive only items corresponding to the userrank.

[0196] The user ranking method is not particularly limited. For example,a high rank may be given to a user who frequently uses products of themanufacturer of the objective device 1, or a user who has made userregistration. Also, users may be ranked with reference to data such as ause history, and the like described in the above embodiment.

[0197] In this way, a service received at an identical objective device1 can be changed depending on users. With this function, themanufacturer or dealer of the objective device 1 can provide value-addedservices.

[0198] Eighth Embodiment

[0199]FIG. 26 is a block diagram showing characteristic functions of aninformation processing system according to the eighth embodiment of thepresent invention.

[0200] This embodiment will explain a case wherein a processcorresponding to the level of data to be sent to a user setup datarecording device 2 is executed, e.g., different services are provided bystoring data in the user setup data recording device 2, and changing thenumber of data to be acquired by the objective device 1 for respectiveusers, as shown in FIG. 26, as an example of a process for identifying auser who accesses the objective device 1, and executing a process foreach user.

[0201] The flow charts showing the operation of the objective device 1according to this embodiment use FIGS. 19 and 27. The difference betweenFIGS. 20 and 27 is that a process in step S2700 is added. In thisembodiment, the difference will be supplemented.

[0202] The seventh embodiment has explained the method of providingservices that limit the number of items which can be used depending onusers (for example, device setup data for a given objective device 1includes 10 items, and the objective device 1 allows user α to makesetups using all 10 items, but allows user β to make setups using onlythree items). However, this embodiment provides such services by anothermethod.

[0203] In this embodiment, data to be sent from the objective device 1to the user setup data recording device 2 undergoes a processcorresponding to a pertinent level (step S2700 in FIG. 27), and is thensent (step S2003).

[0204] In the process in step S2700, items used in steps are changed.The objective device 1 or the authentication server 3 that cancommunicate with the objective device 1 saves data for ranking users,and processes executed in correspondence with the ranks of users. Forexample, the user rank includes S (highest), A, B, C, and D (lowest). Inthe process corresponding to the user rank, if device setup data of agiven objective device 1 has 10 items, the user of rank S can makesetups of the objective device 1 using all the 10 items, the user ofrank A can use 8 items, the user of rank B can use 6 items, the user ofrank C can use 4 items, and the user of rank D can use only 2 items.

[0205] Upon executing this process, the objective device 1 may receiveand process user setup data of all the 10 items from the user setup datarecording device 2, or may receive only items corresponding to the userrank. This depends on implementation contents of step S2700, i.e.,processes to be done in correspondence with ranks.

[0206] The user ranking method is not particularly limited. For example,a high rank may be given to a user who frequently uses products of themanufacturer of the objective device 1, or a user who has made userregistration.

[0207] The objective device 1 sends authentication data, device ID data,and data generated by the process in step S2700 to the user setup datarecording device 2. In this embodiment, only items of device setup datacorresponding to a pertinent rank are sent as data generated in theprocess in step S2700. Upon receiving blank device setup data, the usersetup data recording device 2 returns items and values of user setupdata corresponding to the items of the received device setup data.

[0208] The objective device 1 receives the user setup data. At thistime, since the objective device 1 receives user setup datacorresponding to the user rank, it executes a setup process based on thereceived items and values.

[0209] In this way, a service received at an identical objective device1 can be changed depending on users. With this function, themanufacturer or dealer of the objective device 1 can provide value-addedservices.

[0210] Since the number of items of device ID data to be sent from theobjective device 1 to the user setup data recording device 2 can bereduced, a high transmission rate and short data processing time can beachieved due to the reduced transmission data size.

[0211] Ninth Embodiment

[0212]FIG. 28 is a block diagram showing characteristic functions of aninformation processing system according to this embodiment.

[0213] This embodiment will explain a case wherein data to be sent froman objective device 1 to a user setup data recording device, and datareceived from the user setup data recording device respectively undergoprocesses corresponding to their respective levels, as shown in FIG. 28,as an example of a process for identifying a user who accesses theobjective device 1, and executing a process for each user. Morespecifically, a service provided when the objective device 1 changes aprocess according to data obtained by searching databases shown in FIGS.29A and 29B which are prepared in the user setup data recording device 2will be explained below.

[0214] As shown in the image in FIG. 30, assume that the objectivedevice 1 is an air conditioner, and is set up on the basis of the setupsof users who belong to a given group. These users are ranked. In thisembodiment, the group that uses the objective device 1 includes twousers, i.e., user A with authentication data “OijdiOI” and user B withauthentication data “AoijOJ”. In the objective device 1, authenticationdata of these users are registered as a group.

[0215] The flow charts of the objective device 1 according to thisembodiment use FIGS. 20 and 31. The difference between FIGS. 20 and 31is that processes of steps S3110, S3101, and S3102 are added. In thisembodiment, transmission to a plurality of users is used.

[0216] The flow of the processes of this embodiment from a re-setupsituation will be explained in detail below.

[0217] The user sets the objective device 1 in an initial state byturning on its power supply 192. User A presses the finger 4 against thefingerprint sensor 107 of the objective device 1. The fingerprint sensor107 is activated upon detecting touch with the finger 4 (step S1). Ifthe sensor is activated, it checks if a registration start action hasbeen done (step S2). In this case, assume that the registration startaction has not been done.

[0218] Since the registration start action has not been done, physicalinformation can be read (step S4). If read has failed, the controlreturns to the initial state. The read data is temporarily saved in theRAM 102, and is converted into the authentication data “OijdiOI” by thedata converter 104 (step S5). If fingerprint information is directlyused in personal identification without being converted intoauthentication data, this data conversion process may be skipped. Whenthe CPU 101 can perform data conversion, the data converter 104 may beomitted. Furthermore, the data conversion process may include a securityprocess such as encryption. The converted authentication data is storedin the RAM 102.

[0219] Since the registration start action has not been done, no datawhich can be registered is sent (step S6).

[0220] An authentication process is done inside or outside the objectivedevice 1. A supervisor of the objective device 1 must set in theobjective device 1 information indicating whether fingerprintauthentication is done inside or outside the objective device 1, incorrespondence with the structure and operating environment of theobjective device 1 (step S1901). In this embodiment, the authenticationprocess is executed inside the objective device 1.

[0221] When fingerprint authentication is executed inside the objectivedevice 1, the pattern matching unit 103 compares authentication data,which is generated by acquiring fingerprint information by the sensorand is stored in the RAM 102 and the registered authentication datastored in the flash ROM 106 (step S1904). If the flash ROM 106 storesauthentication data which matches that in the RAM 102, the user has theright of use of the objective device 1; otherwise, the user does nothave such right. If the user has the right of use, the flow advances tostep S2001 in FIG. 31; otherwise, the control returns to the initialstate. In this embodiment, user level classification is also done instep S1904. Assume that user A is registered in the objective device 1as level B, and user B who appears later as level S. Therefore, if theauthenticated user is user A, his or her level is classified to level B.

[0222] The objective device 1 then checks if it broadcasts device setupdata (step S2001).

[0223] The objective device 1 records in the RAM 102 informationindicating if broadcast was made. Whether or not broadcast is made isexpressed by whether authentication data is appended or not to data tobe transmitted. Since this embodiment uses a wireless communicationmeans, if data is merely sent using an identical frequency, data isdistributed to all objective devices 1 and user setup data recordingdevices 2 which are present around the source objective device 1. Inthis embodiment, assume that broadcast is not to be made.

[0224] Then, a process for each user is executed (step S3100). In thisembodiment, since the user who touched the sensor of the objectivedevice 1 is user A, whose rank is B, only an item “temperature” ofdevice setup data of the objective device 1 is reflected in actualsetups.

[0225] In this embodiment, since broadcast is not made, the objectivedevice 1 sends the authentication data in the RAM 102, device ID data inthe startup ROM 105 or flash ROM 106, and device setup data of only theitem “temperature” determined by level B of user A to the user setupdata recording device 2 (step S2003). Data to be sent is as shown inFIG. 32. Upon sending data, the authentication data stored in the RAM102 is converted into an appropriate communication protocol in the CPU101, and is sent via the data transmitter 113 and wireless I/F 111 usingthe wireless channel 5.

[0226] After the data is sent (step S2003), it is checked if identicaldevice ID data is to be sent to a plurality of users (step S2004). Thechecking process in step S2004 is effective when the setups of onlygiven group members are to be reflected in a given objective device 1 inplace of unspecified setups within the communication range of theobjective device 1.

[0227] If it is determined in step S2004 that the data is to be sent toa plurality of users, the authentication data is replaced by that forthe group members (step S2005), and the replaced data is sent (stepS2003). The group members are set in advance in the objective device 1.

[0228] In this embodiment, the group that uses the objective device 1includes two users, i.e., user A with authentication data “OijdiOI” anduser B with authentication data “AoijOJ”. In the objective device 1,authentication data of these users are registered as a group. Since userA has operated the sensor of the objective device 1, the objectivedevice 1 sends the data also to user B as a member of the group.

[0229] The objective device 1 replaces the authentication data by thatfor user B (step S2005). The level of user B is registered as S in theobjective device 1. The objective device 1 searches for the level ofuser B using the authentication data. The level S of user B is read, andas a process corresponding to the level S, items “temperature” and“humidity” of device setup data are reflected in actual setups (stepS3100). The objective device 1 sends data shown in FIG. 33 for user B(step S2003). Since no more group members are registered, NO isdetermined in the process in step S2004, and the control of theobjective device 1 advances to step S2006 as a reply standby state fromthe user setup data recording device 2.

[0230] The processes in the user setup data recording device 2 have beenexplained previously with reference to the flow chart in FIG. 8.

[0231] In this embodiment, the user setup data recording device 2possessed by user A has the database shown in FIG. 29A, and thatpossessed by user B has the database shown in FIG. 29B.

[0232] The user setup data recording device 2 possessed by user Areceives data shown in FIG. 32, and that possessed by user B receivesdata shown in FIG. 33. As for user A, since the device setup dataincludes only the item “temperature”, the user setup data recordingdevice 2 possessed by user A sends device ID data, corresponding usehistory values, and a value “26” of the item “temperature” of user setupdata in FIG. 29A to the objective device 1. The user setup datarecording device 2 possessed by user B sends device ID data,corresponding use history values, and a value “22” of the item“temperature” and a value “10” of the item “humidity” of user setup datain FIG. 29B to the objective device 1.

[0233] The respective user setup data recording device 2 updates usehistory values corresponding to the device ID data received from theobjective device 1. For example, the items of the received device IDdata are compared with those of device ID data already held by the usersetup data recording device 2, and if they match, the corresponding usehistory value is incremented by 1.

[0234] The objective device 1 checks if it can receive data sent withina predetermined period (step S2006). If the objective device 1 cannotreceive any data within the predetermined period, the control returns tothe initial state without any process.

[0235] Since the objective device 1 recorded in the RAM 102 in stepS2001 information indicating that it broadcasted data or sent data to aplurality of users, if it broadcasted data or sent data to a pluralityof users, the received data is processed as a reply thereto; otherwise,the received data is processed as a reply from a single user (stepS3102). In this embodiment, the objective device 1 waits for andreceives replies from the user setup data recording devices 2 of users Aand B.

[0236] The objective device 1 compares if the device ID data containedin the received data matches its own device ID data. If the two datamatch, since the received data is a reply to the data sent by theobjective device 1 itself, and a process is executed; otherwise, thereceived data is discarded. Note that items of the device ID data to beactually compared in a search are not specified in the abovedescription, but they may be determined by the manufacturer of the usersetup data recording device 2 or may be of user's choice.

[0237] If broadcast was not made (step S3102), the objective device 1 isset up again on the basis of the received user setup data, and thecontrol returns to the initial state.

[0238] If broadcast was made (step S3102), a plurality of received usersetup data are statistically processed (step S2008), and the objectivedevice 1 is set up again on the basis of the statistical processingresult (step S2009). The control then returns to the initial state.

[0239] In this embodiment, data was not broadcasted but was sent to aplurality of users. Hence, NO is determined in step S2007, and a processfor each user is executed in step S3101. The objective device 1 receivesonly the value “26” of the item “temperature” for user A, and the value“22” of the item “temperature” and the value “10” of the item “humidity”for user B in addition to the device ID data and use history valuescorresponding to the items of the device ID data. The level of user A isB, and that of user B is S.

[0240] The objective device 1 executes a process corresponding to theuser level (step S3101). As for humidity, since the objective device 1receives “10” alone as the user setup data of user B, it is set to have“humidity” of “10”%. Then, temperature is set. The setup values oftemperature are received from both users A and B. The levels of users Aand B are compared. If the users have identical level, the sum total ofthe values is simply divided by the number of users. For example, ifusers A and B have identical level, since the received values are “26”and “22”, the objective device 1 is set to attain “24” degrees.

[0241] However, user A has rank B, and user B has rank S. Hence, aprocess that preferentially uses the user setup data of rank S isexecuted. For example, “23” degrees may be set to be closer to the usersetup data of user B with higher rank than “24” degrees as the averageof the two users, or the user setup data of user A is ignored, and “22”degrees may be set. Although not exemplified, the objective device 1receives use histories of the respective users with respect to theobjective device 1. Hence, the process according to the level may beexecuted in step S3101 in consideration of the use histories of theusers. For example, user setup data of a user with larger use historyvalues may be reflected in the objective device 1 more easily.

[0242] The process executed in step S3101 depends on implementationcontents of the manufacturer of the objective device 1. This embodimentis one example. In the above example, data to be updated by device IDdata is the use history. Of course, other items may be updated. Forexample, the number of times of charge, date, and the like may beupdated.

[0243] When programs according to the flow charts of the respectiveembodiments are stored in, e.g., the flash ROM 106 in the objectivedevice 1 to operate the objective device 1, the control methods of theabove embodiments can be implemented.

[0244] The objective device 1 and user setup data recording device 2 canbe added with a function of encrypting data to be sent. In this case, adata encryption function is required. Encryption may be done by the CPU101, or a dedicated chip for encryption may be prepared. At the sametime, if data is encrypted, the objective device 1 and user setup datarecording device 2 must have a function of receiving encrypted data, anddecrypting that data. Data decryption may be done by the CPU 101 or adedicated chip for decryption may be prepared. In the present invention,such schemes are not particularly limited.

[0245] When data is encrypted, the security of communication data can beimproved compared to a case wherein data is exchanged without beingencrypted. If public key cipher is adopted as an encryption scheme, andthe objective device 1 generates a secret key based on sensorinformation, the data can be used not only in encryption but also inuser authentication and specification of the user setup data recordingdevice 2.

[0246] In the above embodiments, the objective device 1 has the sensor107. This is to assure data security and to use the device as a userinterface. That is, since the objective device 1 comprises the sensor,personal identification and authentication can be made, and the usersetup data recording device 2 cannot be used if it is acquired by athird party, thus protecting setup data which reflects user's favor.

[0247] Furthermore, the sensor 107 and level classification means canexecute authentication to identify a user who accesses the objectivedevice 1, and different processes for respective users can be executed.Moreover, a user interface which can set up the objective device 1 inresponse to only user's action upon reading the physical informationusing the sensor can be provided.

[0248] When the sensor 107 detects the user, it reads the physicalinformation of that user to generate authentication data. The objectivedevice 1 itself or the authentication server compares the alreadyregistered authentication data with the generated authentication data tomake authentication. As a result of authentication, if the user has theright of use, the objective device 1 executes a process corresponding tothe level as needed, and sends authentication data, device ID data, andthe like to the user setup data recording device 2. If the user has nosuch right, no data is sent.

[0249] The user setup data recording device 2 makes personalidentification, i.e., checks using the authentication data if the usersetup data recording device 2 is that of the current user. If no problemis found as a result of personal identification, the user setup datarecording device 2 searches for user setup data corresponding to theobjective device 1 using the previously received device ID data as akey. If the corresponding user setup data is found, the user setup datarecording device 2 sends the user setup data and device ID data. Theobjective device 1 receives the user setup data, executes a processcorresponding to a level as needed, and executes a setup process on thebasis of the received user setup data.

[0250] Therefore, the user can undergo personal identification andauthentication by reading physical information using the sensor. Thatis, the user can send setups of the objective device 1, which have beenregistered in the user setup data recording device 2 once to theobjective device 1 to set it up, when the sensor detects the user.

[0251] In the above embodiments, the digital camera and air conditionerare set up. Electronic devices that can undergo the above setup processare not particularly limited. For example, the present invention can beapplied to various use objects and use situations such as {circle over(1)} the angle and position of a vehicle seat, {circle over (2)} theangle of the seatback, and the method, strength, and position of massageof a massage chair, {circle over (3)} setups of the tone volume,surround type, and loudspeaker direction of a sound device, {circle over(4)} video recording setups of types of programs that are frequentlyrecorded by a video recorder, 5{circle over (5)} the degree anddirection of illumination of an illumination appliance, {fraction (6)}the level and temperature of a bath, 7{circle over (7)} the temperature,wind speed adjustment, and the like of an air conditioner, {circle over(8)} a copying machine and printer, and the like.

[0252] For example, when the objective device is a device which isconnected to a network to upload data (e.g., a digital camera, digitalvideo camera, or portable telephone), the user setup data recordingdevice sends an upload destination URL (FIG. 34) as user setup data tothe objective device, thus uploading data in the objective device to theupload destination URL.

[0253] For example, if the objective device is a digital camera, whenthe user touches the shutter of the digital camera (objective device)with a finger, data shown in FIG. 34 is sent form the user setup datarecording device to the digital camera. When the user takes a photo, thedigital camera looks up an image saving destination URL designated bythe user setup data, and transfers the taken image file. The image fileis sent, and is automatically saved.

[0254] As a result, the upload destination URL corresponding to thedevice is correctly set, and the user can save a taken image at thedesignated URL irrespective of a digital camera he or she used to take aphoto.

[0255] When the objective device is a printer at user's destination(e.g., on a street corner), and when the user touches an auto printbutton, the user setup data recording device sends a URL registeredtherein by the user to the objective device as user setup data (FIG.35).

[0256] The printer as the objective device downloads and prints datafrom a server at the designated URL. With this arrangement, a specificnewspaper or the like can be printed by a nearby printer when the usertouches it.

[0257] Hence, the user need only touch the printer to easily print datahe or she ordinarily looks up without any data transfer operation.

[0258] When the objective device is a network-connected device notebookPC, portable telephone, PDA, PC, or the like, and when the user touchesa network connection button, the user setup data recording device sendsa telephone number of a dial-up destination, which is registered thereinby the user, to the objective device as user setup data. The objectivedevice can install the dial-up destination designated as the user setupdata as a telephone number of an access point for network connection.

[0259] Consequently, the user need only touch the notebook PC at his orher destination to connect the access point or service provider he orshe ordinarily uses.

[0260] When the objective device is a driver's seat of a vehicle, andwhen the user touches an authentication section of that seat with afinger, the user setup data recording device sends seat adjustmentinformation, which is registered therein by the user, to the objectivedevice as user setup data (FIG. 37).

[0261] The seat adjusts the angle of a seatback, the up-and-down andback-and-forth positions of the seat, and the angle of a headrest on thebasis of the received data.

[0262] As a result, the user need only touch the seat to set the seataccording to his or her favor.

[0263] When the objective device is a massage chair, and when the usertouches an authentication section of that massage chair, the user setupdata recording device sends massage chair adjustment information, whichis registered therein by the user, to the objective device as user setupdata (FIG. 38). The massage chair adjusts the angle of a seatback, theangle of a footrest, the strength of foot vibration, the operation time,massage type, strength, and schedule on the basis of the received data.

[0264] As a result, the user can undergo massage with his or herfavorite massage method and schedule.

[0265] In the above embodiments, the fingerprint sensor for measuring afeature of a body is used as the sensor. Of course, various othersensors may be used. For example, since the iris pattern of a human eyehas a personal difference as in fingerprints, an iris sensor may beattached to a viewfinder of a digital camera, and when the user looksinto the viewfinder, the iris sensor may be activated to generate imageinformation data of the iris pattern or authentication data as converteddata.

[0266] Furthermore, as still another embodiment, DNA informationcontained in human hair, sputum, sweat, or the like may be used. SinceDNA information has a personal difference, a hair, sputum, or sweatsensor may be arranged to read DNA information and to generateauthentication data. Moreover, since voiceprints also have a personaldifference, a microphone (sensor) may be provided to the objectivedevice to sample voiceprints from a user's voice and to generateauthentication data based on the sampled voiceprint information.

[0267] In this embodiment, the digital camera and wristwatch are assumedas forms of the objective device and user setup data recording device.However, the present invention can be applied even when they have otherforms. For example, examples of the objective device include anillumination appliance, sound system, seat, and the like in addition tothe digital camera. Examples of the user setup data recording deviceinclude a portable telephone, PDA, portable music player, and the like.Note that items of device setup data exchanged between the objectivedevice and user setup data recording device differ depending on thetypes of objective devices 1. For example, when the objective device 1is a sound device, items “tone volume”, “surround mode type (Movie,Hall, and the like)”, “loudspeaker direction”, and the like are used inplace of items “shutter speed”, “AF ON/OFF”, and the like.

[0268] In FIGS. 1, 2, 15, and 16, the flash ROMs 106 and 203 are used tosave data, but other recording media such as a hard disk drive (HDD) andthe like may be used. Likewise, the data receivers 112 and 212 and datatransmitters 113 and 213 may be replaced by data transceivers whichintegrate them.

[0269] Also, the wireless transmission scheme, frequency, type, and thelike are not particularly limited. Furthermore, infrared rays, awireless LAN, ultrasonic waves, light, and the like may be used. In thisembodiment, a wireless communication is used as a communication medium,but a wired communication may be used instead. Furthermore, acommunication method using a human body is known, and such method may beused.

[0270] Note that the present invention is not limited to the apparatusof the above embodiments, and may be applied to either a systemconstituted by a plurality of devices, or an apparatus consisting of asingle equipment. The present invention is also achieved by supplying arecording medium, which records a program code of a software programthat can implement the functions of the above-mentioned embodiments tothe system or apparatus, and reading out and executing the program codestored in the recording medium by a computer (or a CPU or MPU) of thesystem or apparatus.

[0271] In this case, the program code itself read out from the recordingmedium implements the functions of the above-mentioned embodiments, andthe recording medium which stores the program code constitutes thepresent invention. As the recording medium for supplying the programcode, for example, a floppy disk, hard disk, optical disk,magneto-optical disk, CD-ROM, CD-R, magnetic tape, nonvolatile memorycard, ROM, and the like may be used. The functions of theabove-mentioned embodiments may be implemented not only by executing thereadout program code by the computer but also by some or all of actualprocessing operations executed by an OS (operating system) running onthe computer on the basis of an instruction of the program code.

[0272] Furthermore, the functions of the above-mentioned embodiments maybe implemented by some or all of actual processing operations executedby a CPU or the like arranged in a function extension board or afunction extension unit, which is inserted in or connected to thecomputer, after the program code read out from the recording medium iswritten in a memory of the extension board or unit.

[0273] As a case (prior art) combined with fingerprints described in theabove embodiments, a technical article “user interface based onfingerprint recognition” (“Interaction “99”, pp. 169-176, March, 1999)is known. In this article, a technique “Finger Storage (Finger Memo)”has been proposed. As a feature of “Finger Storage”, “data can be copiedbetween different terminals via a finger”.

[0274] However, as a practical implementation method of “FingerStorage”, “when a finger touches another terminal, matching is made witha fingerprint pattern in a Finger ID Table, and a data objectcorresponding to that finger is acquired via a network”. “FingerStorage” holds pairs of fingerprint patterns and data as the Finger IDTable, and a fingerprint pattern is used to search for data. In otherwords, when only fingerprints of hands are used, a maximum of 10 pairscan only be held.

[0275] By contrast, the present invention is not limited to 10 pairsunlike “Finger Storage” since the fingerprint and data are not paired.The present invention uses device ID data (e.g., a serial number,product name, and the like) as a search key upon searching for datasaved in the user setup data recording device, while “Finger Storage”searches for data using a fingerprint pattern as a key.

[0276] As described above, according to the present invention, the needfor user's manual re-setup operations every time the user uses a devicehe or she set it once can be obviated. Also, the user is free from anyaction for selecting data from several patterns of setup data.

[0277] The supervisor or the like of the objective device (electronicdevice) can limit user's access to the objective device withoutimpairing user's operability. With this access limitation, differentservices can be provided for respective users.

[0278] As many apparently widely different embodiments of the presentinvention can be made without departing from the spirit and scopethereof, it is to be understood that the invention is not limited to thespecific embodiments thereof except as defined in the appended claims.

What is claimed is:
 1. A system having a plurality of devices, comprising: first transmission means for transmitting specific information of a first device to a second device; second transmission means for transmitting setup data according to the specific information transmitted by said first transmission means to the first device; and change means for changing a setup of the first device upon executing a predetermined function on the basis of the setup data transmitted by said second transmission means.
 2. The system according to claim 1, wherein said first transmission means transmits the specific information together with identification information that specifies a user of the first device.
 3. The system according to claim 2, wherein said second transmission means transmits the setup data in accordance with the identification information transmitted by said first transmission means.
 4. The system according to claim 2, wherein said second transmission means transmits the setup data according to a level based on the identification information transmitted by said first transmission means.
 5. The system according to claim 2, wherein said change means changes in accordance with a level based on the identification information transmitted by said first transmission means.
 6. The system according to claim 1, further comprising: acquisition means for acquiring identification information of a user who uses the first device, and wherein said first transmission means transmits the specific information together with the identification information acquired by said acquisition means.
 7. The system according to claim 6, wherein said acquisition means acquires physical information of the user.
 8. The system according to claim 1, wherein the setup data transmitted by said second transmission means can be registered from the first device in the second device.
 9. The system according to claim 1, wherein said change means changes in accordance with a level of a user who uses the first device.
 10. The system according to claim 1, wherein said change means changes in accordance with the number of times a user who uses the first device used the first device.
 11. A system having a plurality of devices, comprising: first transmission means for transmitting identification information that specifies a user of a first device to a second device; second transmission means for transmitting setup data to the first device in accordance with the identification information transmitted by said first transmission means; and change means for changing a setup of the first device upon executing a predetermined function on the basis of the setup data transmitted by said second transmission means.
 12. The system according to claim 11, wherein said first transmission means transmits the identification information together with specific information of the first device.
 13. A first device which can execute a predetermined function, comprising: transmission means for transmitting specific information of said first device to a second device; reception means for receiving setup data transmitted by the second device in accordance with the transmitted specific information; and change means for changing a setup upon executing the predetermined function on the basis of the setup data received by said reception means.
 14. The device according to claim 13, wherein said transmission means transmits the specific information together with identification information that specifies a user of said first device.
 15. The device according to claim 13, wherein said change means changes in accordance with a level based on the identification information transmitted by said transmission means.
 16. The device according to claim 13, further comprising: acquisition means for acquiring identification information of a user who uses said first device, and wherein said transmission means transmits the specific information together with the identification information acquired by said acquisition means.
 17. The device according to claim 16, wherein said acquisition means acquires physical information of the user.
 18. The device according to claim 13, further comprising: registration means for registering the setup data in the second device.
 19. The device according to claim 13, wherein said change means changes in accordance with a level of a user who uses said first device.
 20. The device according to claim 13, wherein said change means changes in accordance with the number of times a user who uses said first device used said first device.
 21. A first device which can execute a predetermined function, comprising: transmission means for transmitting identification information of a user who uses said first device to a second device; reception means for receiving setup data transmitted by the second device in accordance with the transmitted identification information; and change means for changing a setup upon executing the predetermined function on the basis of the setup data received by said reception means.
 22. The device according to claim 21, wherein said transmission means transmits the identification information together with specific information of said first device.
 23. A second device which can change a setup of a first device, comprising: reception means for receiving specific information of the first device transmitted by the first device; and transmission means for transmitting setup data in accordance with the specific information received by said reception means, wherein the setup data to be transmitted by said transmission means is data used by the first device to change a setup upon executing a predetermined function.
 24. The device according to claim 23, wherein said transmission means transmits the setup data in accordance with identification information that specifies a user of the first device transmitted from the first device.
 25. The device according to claim 24, wherein said transmission means transmits the setup data according to a level based on the identification information.
 26. The device according to claim 23, wherein the specific information is physical information of a user who uses the first device.
 27. The device according to claim 23, wherein the setup data is data registered by the first device.
 28. The device according to claim 23, wherein said transmission means transmits the setup data according to a level of a user who uses the first device.
 29. The device according to claim 23, wherein said transmission means transmits the setup data according to the number of times a user who uses the first device used the first device.
 30. A second device which can change a setup of a first device, comprising: reception means for receiving identification information that specifies a user of the first device transmitted by the first device; and transmission means for transmitting setup data in accordance with the identification information received by said reception means, wherein the setup data to be transmitted by said transmission means is data used by the first device to change a setup upon executing a predetermined function.
 31. A method of controlling a first device which can execute a predetermined function, comprising: the transmission step of transmitting specific information of the first device to a second device; the reception step of receiving setup data transmitted by the second device in accordance with the transmitted specific information; and the change step of changing a setup upon executing the predetermined function on the basis of the setup data received in the reception step.
 32. A method of controlling a first device which can execute a predetermined function, comprising: the transmission step of transmitting identification information of a user who uses the first device to a second device; the reception step of receiving setup data transmitted by the second device in accordance with the transmitted identification information; and the change step of changing a setup upon executing the predetermined function on the basis of the setup data received in the reception step.
 33. A method of controlling a second device which can change a setup of a first device, comprising: the reception step of receiving specific information of the first device transmitted by the first device; and the transmission step of transmitting setup data in accordance with the specific information received in the reception step, wherein the setup data to be transmitted in the transmission step is data used by the first device to change a setup upon executing a predetermined function.
 34. A method of controlling a second device which can change a setup of a first device, comprising: the reception step of receiving identification information that specifies a user of the first device transmitted by the first device; and the transmission step of transmitting setup data in accordance with the identification information received in the reception step, wherein the setup data to be transmitted in the transmission step is data used by the first device to change a setup upon executing a predetermined function. 